Release 10.1A: OpenEdge Getting Started:
Installation and Configuration

Progress Explorer framework overview

The Progress Explorer Framework is a system administration framework that provides a consistent interface in which OpenEdge server products are managed.

Table 10–1 identifies each element of the Progress Explorer Framework, briefly defines the element, and points to other sections within this document where additional information about an element is presented. Figure 10–1 complements Table 10–1, showing the conceptual relationship among the framework’s elements.

Table 10–1: Elements of the OpenEdge Application Framework

Element	Description	For detailed information about this element, see. . .
AdminServer1	As the central control within the framework, the AdminServer: Manages each instance of an installed OpenEdge server2 product by providing administrative access to OpenEdge products installed on your network. Governs remote management and configuration capabilities. Supports an administrative feature which users can set to limit access to OpenEdge products.	"Getting started with the AdminServer" section (Windows platforms), "Getting started with the AdminServer" section (UNIX platforms), Chapter 11, "Configuring OpenEdge Unified Broker Products," and Appendix G "AdminServer Authorization and Authentication."
Progress Explorer configuration tool3	A graphical user interface tool to: Initiate administrative tasks on local or remote machines that require a running AdminServer. Perform a variety of administrative, managerial, configuration, and validation activities for OpenEdge products. The Progress Explorer only runs in Windows. However, you can connect to remote UNIX systems and administer various supported components on those remote UNIX systems.	"Using the Progress Explorer tool" section and Chapter 11, " Configuring OpenEdge Unified Broker Products." Also, see the Progress Explorer online help for extensive information about using the tool.
Mergeprop utility3	A command-line utility that supports functionality similar to that supported by the Progress Explorer configuration tool. The mergeprop utility can be used as an alternative approach when the Progress Explorer configuration tool is not available.	"Mergeprop utility overview" section.
Command-line utilities3	A basic command-line tool that allows you to control (that is, start, stop, and query) servers and validate property files associated with OpenEdge products.	"Command-line utilities reference" section.
ubroker.properties file3 (Unified Broker properties file)	Common text file location in which data for each Unified Broker4 product is stored. The Progress Explorer’s and the mergeprop utility’s capabilities can be applied to the contents of the ubroker.properties file to manage, configure, or validate properties for each of these products. The ubroker.properties file is located in $DLC/properties/ directory.	"Ubroker.properties file and product configurations" section and Chapter 11, " Configuring OpenEdge Unified Broker Products."
conmgr.properties file (Configuration Manager properties file)	Common text file that contains configuration information for all OpenEdge databases5. The Progress Explorer’s and mergeprop utility’s capabilities can be applied to the contents of the conmgr.properties file to manage, configure, or validate properties for each of these products. The conmgr.properties file is located in $DLC/properties/ directory.	"Ubroker.properties file and product configurations" section and Chapter 11, " Configuring OpenEdge Unified Broker Products."
AdminServer plugins.properties file	Common text file that contains information for plugins to be loaded and managed by the AdminServer. The AdminServer plugins.properties file is located in $DLC/properties/ directory.	"Changing the default port" section.
JavaTools.properties file (OpenEdge clients’ configuration file)	Common text file that contains configuration information for all OpenEdge clients. The JavaTools.properties file is located in $DLC/properties/ directory.	Do not make user-modifications to these property files as these properties support OpenEdge and Progress products only. Contact Progress Technical Support if you want to modify these properties.

1The AdminServer must be running to use the management command-line management utilities (such as ASBMAN, DBMAN, NSMAN, and WTBMAN) or the Progress Explorer configuration tools. Only mergeprop and the Progress Explorer configuration tool perform the actual configuration of Progress server products and such changes affect the data stored in the ubroker.properties or conmrg.properties files. 2See the "OpenEdge products supported by the AdminServer" section (Windows platforms) and the "OpenEdge products supported by the AdminServer" section (Unix platforms) for specific products. 3Commands entered and accepted either through the Progress Explorer tool or the mergeprop tool immediately affect the data stored in the ubroker.properties file or conmrg.properties file. 4The Unified Broker products includes these OpenEdge servers: AppServer, WebSpeed, NameServer, and the Oracle DataServer, the DataServer for MS SQL, amd the DataServer for ODBC. 5Only those OpenEdge databases that are configured to autostart will start when the AdminServer starts.